Comments (9)
IMHO, there's nothing wrong with starting again. We learn from our work, discover things that work well, discover things that don't work well, and sometimes want to take a difference approach to our projects in the future. But, if starting again, I would recommend one of two options: Either (1) all tags/releases which already exist to continue to exist, and increment the major version for the restart (i.e., start again at v3.0.0), or, if really determined to start again at v1.0.0.. (2) give it a minor rebranding (e.g., NewZest? ReZest? NuZest..? Okay.. Those name ideas are actually kind of weak, and kind of suck a bit, and I'm not really sure what would be best insofar as names go.. but you get the point).
But, I would not recommend re-releasing a specific tag/version for a package when that particular package has already had an identical tag/version released in the past, under the exact same package name, because it can potentially cause confusion for some users, feels a little strange, and conversations in the future about the package.. when talking about such-and-such version, when there has been restarts, not just of the code, but also of the tags/versions/releases, participants in the conversation may need to ask to confirm.. "Are we talking about such-and-such from before, or from after the restart?"
Maybe other people will have different opinions, different views about this, and that's fine. Such things are subjective, and not an exact science. But at least, that's my opinions/views about it.
I had a similar situation with one of my own projects: phpMussel. (Actually.. I had this situation occur twice before for that particular project.. 👀 but everything has worked out in the end, so no worries). But.. talking about the second time it happened: For major versions 1 and 2, phpMussel existed as a single repository, and had its own integrated updater built into it, which I'd designed myself. But, for various reasons, I wanted to completely overhaul the entire package, use some different programming paradigms, split the package up into several different distinct repositories/packages (so, not all just as a single repository anymore), and rework it to be more oriented around Composer, rather than around its own updater (which I also consequently removed entirely, because its own updater wasn't quite compatible with the way Composer works). Because some of the new repositories/packages had the same/similar names as certain parts of the old repository, to avoid any ambiguity and potential confusion, I started those new repositories at v3, rather than going back to v1. (The old repository continues to exist, but as a metapackage, to orchestrate requirements/installations for the various packages which replace it for v3 onward). I probably could've just started at v1, and I guess, many other people would've done that, but seeing as I wasn't rebranding anything, I decided to continue with the existing line of tags/releases.
- Security features (CSRF, XSS).
- Package system (So, we can integrate any third party Database ORM)
Both of these things are good ideas. :-)
from framework.
Sounds like a good plan. 👍
from framework.
@Maikuolan Thanks for great explainations and response.
Yes we should stick with the version, so instead of v2.0.4, I think the point I mentioned after completing those we can launch v3.0.0 version.
from framework.
v2.0.3 was released 26th August 2018, and there's been numerous changes to the codebase since that time.
Given there was some new changes as recently as last week (renaming the default branch from
master
tomain
), maybe it would be worthwhile to create a new tag/release around now? @lablnet
Thanks for your concern, Let me tell you what I was thinking, your feedback will matter for me OfCouse.
I was thinking to re-release Zest Framework from initial version 1.0.0, because in Past the framework was not stable at all, I have few things in my mind after which I will consider the framework stable, these things are as follow:
- Security features (CSRF, XSS).
- Package system (So, we can integrate any third party Database ORM)
What do you think?
from framework.
I just changed the name from Zest
to AlphaZ
Coz Zest framework is dead! should we consider it as successor of so called Zest
and continue release cycles or from start.
What do you think
@Maikuolan
@peter279k
from framework.
Is the Zest be compatible with AlphaZ? I think it's okay to change name and keep Zest framework features.
from framework.
Is the Zest be compatible with AlphaZ? I think it's okay to change name and keep Zest framework features.
Yes OfCouse, the actual motive is that as this framework is not stable
so it's useless to release 3.0.0 so I changed the name and we starts with 1.0.0
from framework.
Do you mark this abandoned? Please refer the documentation.
from framework.
Do you mark this abandoned? Please refer the documentation.
Not yet, because I lose my Google Authentactor data so I am unable to login to packageist there is no way to reset that! I've contact them Let's see when they reply me.
from framework.
Related Issues (20)
- enhancing the Time class unit tests
- Enhancement of Arrays class HOT 5
- Be flexible for the format inside Time class
- Permission denied after installing Zest framework HOT 6
- Database Package
- Test's for container class
- Enchantment of str class HOT 4
- Error Expection class not found in Redirect.php
- Bug in \Arrays class HOT 10
- Enchantment of \Str class
- SodiumException: key size should be SODIUM_CRYPTO_SECRETBOX_KEYBYTES bytes HOT 3
- Wrong Behaviours of Str \hasUpperCase and \hasLowerCase HOT 2
- Cloudcov key is in the travis config HOT 4
- After adding \Site\Key classs tests failing HOT 6
- Enhancement of Whoops Package
- Fix deprecated PSR-4 autoloading
- Tests are failing on Scrutinizer HOT 2
- Package management extends of container
- Adding static code analysis tool support
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from framework.