Alpha1 release planning about r4mvc HOT 8 CLOSED

The project should be almost ready for alpha1, actually.

#20 and #4 can actually be moved to the v1 backlog, as they're not critical for the alpha. Other than testing a couple issues, the current codebase should work, and has 90% of the core features already. I'd potentially consider #13 and #33 for at least alpha.2 if not alpha.1.

The issues I want to add to the alpha.1 milestone at this point are #51 (just to make sure that part of the code is stable and consistent) and #52 (the simple first workaround with the uninstall script, and once released we'll move #52 to the v1 backlog for a final solution)

P.S. I'll be a bit busy in the coming two weeks, so my progress will be a little slower, but I'm still 100% committed to the project. We should be able to go ahead with alpha one early next week, at which point I'll start working on cleaning the code and adding unit tests.

from r4mvc.

I believe I started with version 0.5 when I rebuilt the projects, and was slowly increasing it as I was adding more features.

I'm OK with bumping it to 1.0 for the alpha then. I'll finish up some tests to make sure it's usable, and deploy the alpha build in the coming days!

from r4mvc.

@artiomchi thanks for your efforts so far. I'll try to find some time over the next week or so to get the CI sorted.

from r4mvc.

@kevinkuszyk @davidebbo
Since the alpha1 release is basically impending, I thought to bring the last thing we should do before pushing the package to NuGet - the package description.

I'm just pushing a commit that cleans up the .csproj on both packages, separating the metadata in a separate property group. I've based the metadata on the current T4MVC packages, since it's practically the same project, with just small adjustments.

Here's what I have so far:

The description on T4Mvc.Tools is:

R4Mvc is a tool that generates strongly typed helpers for ASP.NET Core MVC.

from r4mvc.

@artiomchi looks good. A couple of questions:

1. Are we going to set the initial version to 1.0.0-alpha1?
2. Can you include Scott Mackay (@wwwlicious) as an author - he wrote most of the original code.
3. Do you want to add yourself as an author and owner? Once we push to NuGet.org I'll add you as an owner of the package there too.

And on the subject of deployments, this is an encrypted API key for nuget.org:

oK/7qSZDyR1umPtWP8zAswwPfIE0FJPeEkkQQMRKj6e6eq0tdEIwbPh37lGBDeSi

For MyGet, yes I already created an account. The push url is

https://www.myget.org/F/r4mvc/api/v2/package

and encrypted API key:

DdgwyUm4/aaCfk28jRGRFgQpqcCp6OvuqCZLZaHjNAPHZuia0+PF01zC8JGpWfe7

from r4mvc.

@kevinkuszyk I was going to keep it at pre 1.0 until we're closer to having the full implementation.. The current first alpha is a bit raw around the edges, and while it's usable, it's still missing a lot of the original functionality in T4MVC, like extensibility, for example.. It also requires some work around tooling (esp the dotnet cli part) which also influenced that decision...

Once I'm more confident with the reliability and we have most of the core functionality in place, we'll up the version to 1.0. Does that sound ok?

Re: author/owner, I can set the Authors field to

Kevin Kuszyk, Scott Mackay, Artiom Chilaru

The owner field can either be set to David, or we can leave it blank (which will copy the value above, and will be overridden anyway in nuget.org)

Does that sound good?

from r4mvc.

I'd be happy to start at 1.0.0-alpha1 or 0.1.0-alpha1. I can't remember where 0.6.0 came from to be honest.

from r4mvc.

@kevinkuszyk @davidebbo @wwwlicious
Alpha1 release is finally out and deployed to NuGet! I've put some basic docs up, so that should allow some people to start using and testing it.

In the meantime, I'm switching gears to prepare for alpha 1.1, where I'll concentrate on code restructuring, cleanup and testing, while we gather some feedback from the alpha testers 😄

from r4mvc.